-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create SECURITY.md #1039
Create SECURITY.md #1039
Conversation
@dongsupark Please describe the security process we do weekly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added Flatcar security process.
Marking as ready for review, which the PR should be after the suggestions are merged. |
Co-authored-by: Dongsu Park <[email protected]>
Co-authored-by: Dongsu Park <[email protected]>
Co-authored-by: Dongsu Park <[email protected]>
Co-authored-by: Thilo Fromm <[email protected]>
Co-authored-by: Thilo Fromm <[email protected]>
SECURITY.md
Outdated
## Daily security runbook for Security team primaries and secondaries | ||
|
||
The runbook below discusses steps for identifying new potential security issues and for making the issues known to the Flatcar project's maintainers and / or the other members of the Security team. | ||
Embargoed issues are recorded in a private issue tracker only accessible by the Security team, while public issues are openly tracked in the [Flatcar project](https://github.com/Flatcar/Flatcar/issues). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line is duplicate of the 11-12nd line above. Let's simply remove it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Primary person should do so:
Every day look into upstream security trackers like below:
gorss
+ RSS feed for this.Whenever we discover any new CVE, we add it to an internal database, and use automation tools to create a new issue about the CVE in Flatcar GitHub issues with labels
security
andadvisory
.If an issue of updating the specific package affected by the new CVE is already open in Flatcar GitHub issues, then unfortunately we need to manually edit the existing issue to add the new CVE.